home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
UTILITY
/
LACE_14.ARJ
/
CREM.DOC
< prev
next >
Wrap
Text File
|
1992-06-09
|
10KB
|
289 lines
CREM: Config.Sys REMarker Program v1.0
A Companion Program to LACE
_______
____|__ | (tm)
--| | |-------------------
| ____|__ | Association of
| | |_| Shareware
|__| o | Professionals
-----| | |---------------------
|___|___| MEMBER
Written by Keith Ledbetter
4240 Ketcham Drive
Chesterfield, VA 23832
(804) 674-0780
(6:00pm - 10:00pm Eastern Time)
Tech Support BBS: Blue Ridge Express
804-790-1675
30 Phone Lines (2400 bd)
Sub-board KEITHL
("J KEITHL")
Electronic mail on GEnie: ORION.MICRO
Compuserve: 72240,1221
AOL: KLedbetter
Program and Documentation are
Copyright (c) 1992 by Keith Ledbetter. All rights reserved.
Portions Copyright Borland, International.
Written with Borland C/C++ 3.0.
Introduction
------------
CREM (Config REMarker) is designed to help out those users
who use LACE in conjunction with QEMM-386, 386^MAX, or BlueMAX.
Because of the way these programs perform their "optimization"
procedures, the LACE method of "selection blocks" won't work.
All of these products get very confused when you try to run an
unmodified, LACE'd CONFIG.SYS through them.
Before CREM, the only way to optimize your multiple
configurations was to manually "comment out" or delete unwanted
lines in your CONFIG.SYS, run the optimization procedure, and
then place the newly-optimized lines back into your LACE
selection blocks. CREM helps speed up this process by quickly
and easily commenting out all "LACE specific" lines in your
CONFIG.SYS file, leaving only one selection block (from your
specification) visible to the optimization program.
How it Works
------------
CREM has two possible command line syntaxes, as follows:
CREM block_number
or
CREM "remove"
"CREM block_number" tells the program to process your CONFIG.SYS
file, commenting out all LACE-specific lines and all selection
blocks EXCEPT the "block_number" that you specify.
"CREM remove" tells the program to remove all comments from your
CONFIG.SYS file that were previously placed there by earlier
invocations of CREM (your own comments will remain untouched).
An Example
----------
Let's assume that you have a CONFIG.SYS file that looks like
this one:
DOS = High
device = c:\qemm\qemm386.sys ram
shell = c:\4dos\4dos.com /p @c:\4dos\4dos.ini
device = c:\utils\lace.sys Center NumOff
device = LACE SelectionBarBackground=RED
device = LACE "C\onfiguration with cache"
device = d:\ms_mouse\mouse.sys /y /s30
device = c:\caches\mycache.sys 4096
device = c:\dos50\ansi.sys
device = c:\dos50\setver.exe
device = LACE "C\onfiguration with RAMdisk"
device = d:\ms_mouse\mouse.sys /y /s30
device = c:\dos50\ramdrive.sys 4096
device = c:\dos50\ansi.sys
device = c:\dos50\setver.exe
device = LACE "B\are-bones configuration"
device = c:\dos50\ansi.sys
device = c:\dos50\setver.exe
device = LACE End
buffers = 5
files = 60
break = on
STACKS = 0,0
lastdrive = E
If you invoked CREM with the command line "CREM 2", your
CONFIG.SYS file would be modified to look like this:
DOS = High
device = c:\qemm\qemm386.sys ram
shell = c:\4dos\4dos.com /p @c:\4dos\4dos.ini
REM {!!}device = c:\utils\lace.sys Center NumOff
REM {!!}device = LACE SelectionBarBackground=RED
REM {!!}device = LACE "C\onfiguration with cache"
REM {!!} device = d:\ms_mouse\mouse.sys /y /s30
REM {!!} device = c:\caches\mycache.sys 4096
REM {!!} device = c:\dos50\ansi.sys
REM {!!} device = c:\dos50\setver.exe
REM {!!}
REM {!!}device = LACE "C\onfiguration with RAMdisk"
device = d:\ms_mouse\mouse.sys /y /s30
device = c:\dos50\ramdrive.sys 4096
device = c:\dos50\ansi.sys
device = c:\dos50\setver.exe
REM {!!}device = LACE "B\are-bones configuration"
REM {!!} device = c:\dos50\ansi.sys
REM {!!} device = c:\dos50\setver.exe
REM {!!}
REM {!!}device = LACE End
buffers = 5
files = 60
break = on
STACKS = 0,0
lastdrive = E
As you can see, only the second selection block will now be
seen by the operating system (and, most importantly, by the
optimization program). You would then run either QEMM's OPTIMIZE
program or 386^MAX's MAXIMIZE program. After you have completed
the optimization step, you would execute the following command:
CREM remove
which would remove the comments placed in your CONFIG.SYS by the
earlier run of CREM, leaving you once again with your old LACE
menu selections (but with a properly optimized second selection
block).
OK..So What about AUTOEXEC.BAT?
-------------------------------
You had to ask that question, didn't you! Unfortunately,
since there are so many ways that you can set up for multiple
AUTOEXEC.BAT processing under LACE, there's really no clean way
to implement an automatic approach to remarking or deleting
unwanted pieces. Because of this, you will still have to handle
the AUTOEXEC.BAT file(s) yourself before running your
optimization program.
If you are using only one AUTOEXEC.BAT file, then the
process will be much easier. Let's say that your AUTOEXEC.BAT
file looks like this:
-----------------------------------------------------------------
c:\lace\lace_set
goto config_%lace%
:config_1
... configuration one lines ...
:config_2
... configuration two lines ...
:config_3
... configuration three lines ...
-----------------------------------------------------------------
Continuing the above example of optimizing configuration block
number two, you could run "CREM 2" to modify the CONFIG.SYS file
(as we did above), and then edit your AUTOEXEC.BAT file to look
like this:
-----------------------------------------------------------------
c:\lace\lace_set
set LACE=2 <--- ADD THIS LINE
goto config_%lace%
:config_1
... configuration one lines ...
:config_2
... configuration two lines ...
:config_3
... configuration three lines ...
-----------------------------------------------------------------
Then, after running the optimize program, merely edit your
AUTOEXEC.BAT file again and remove the "set LACE=2" statement.
You have now fully optimized selection block two.
In Conclusion
-------------
CREM will -ALWAYS- operate on C:\CONFIG.SYS; there's no way
to tell the program to read and write to a file on a different
drive (but, there should never be a need to).
To wrap up, here are the steps you would take to fully
optimize a hypothetical LACE configuration with three different
selection blocks (we'll use QEMM's OPTIMIZE in this example):
1. run "CREM 1"
2. Change AUTOEXEC.BAT for first configuration
3. run "OPTIMIZE"
4. run "CREM 2"
5. Change AUTOEXEC.BAT for second configuration
6. run "OPTIMIZE"
7. run "CREM 3"
8. Change AUTOEXEC.BAT for third configuration
9. run "OPTIMIZE"
10. run "CREM remove"
I hope that CREM will help make the job of managing and
optimizing your LACE configurations much more painless. If you
have any suggestions for future enhancements, please don't
hesitate to contact me about them.
Enjoy!
Keith